Create GH actions workflow for agent release - #3026
Closed
JonasKunz wants to merge 3 commits into
Closed
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
Contributor
Author
|
Closed in favor of #3137 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Add GH actions workflow for our existing release process.
Most of the process is unchanged, main difference is that all commiting / tagging is done in the very first job within the workflow and not during the actual build and deploy anymore.
I added a new automation for moving eveything in the
unreleasedsection in the changelog to a new section for the target release.As a result, we should now be able to retry the individual steps in this workflow, because each one is atomic and retriable in case of failure.
I testes the provided jobs as far as possible without authorization on my own fork.
The following things still need to be done:
mvn deployapmmachineauthorization (or whichever user we use)I have marked all the places with
# TODOcomments in the workflow file where work is needed.